Skip to main content

DCC 7.4

· 9 min read

New Features​

IG-2562 Introducing Assets – Beta​

Release notes​

DCC 7.4 introduces the first Beta implementation of Assets, a new way to represent individual machines, production lines, or other logical units when several of them share the same IoT device or gateway.

Until now, DCC has primarily represented data through the hierarchy IoT device → Collector → Sample Point. This works well when one gateway represents one machine, but less well when a gateway collects data from several independent machines. Assets add a logical layer that allows related sample points to be grouped according to the equipment they actually belong to.

For example, a gateway connected to several production lines can expose each line as a separate Asset in DCC, while still using the same underlying gateway. Assets can also separate sample points belonging to different machines even when those sample points originate from the same PLC or Collector.

In this first MVP, Assets can be created from the IoT device configuration and are shown below their parent IoT device. They can be used in Data Viewer, Next-Gen Dashboards and Fleet Dashboards, selected as the default device or Asset for a dashboard, and configured with reusable Data Refinement Groups.

An Asset always belongs to a single gateway and remains within that gateway's existing access-rights boundary. Combining equipment across multiple gateways is not part of the current Asset model.

This is the first MVP of the Asset functionality. Additional DCC functionality will be added to the Asset model in subsequent iterations as the feature moves beyond Beta.

The new Working with DCC Assets guide available on the documentation site https://documentation.inuatek.com/docs/guides-and-tutorials when 7.4 is live, explains how Assets are created, named, renamed and removed, and how sample points are assigned to them.

IG-2595 Last known values are now carried forward in step-line charts and Value widgets​

Release notes​

Step-line charts and Value widgets can now use the last known value when no new data has been received during the selected time period.

For step-line charts, the last value before the selected period is carried forward from the beginning of the chart. If no new values are received during the period, that value remains visible across the full time range.

Value widgets configured to show the latest value now also display the most recent known value, even when it was received before the selected period. The original timestamp remains available, so the age of the value can still be determined.

This is particularly useful for states or values that only change occasionally, where the absence of a new sample should not be interpreted as missing data.

Regular line charts are unchanged.

Constraint: When looking for a previous value, DCC searches back across up to 10 historical device configurations.

IG-2643 Synchronized scaling is now enabled by default​

Release notes​

For widgets that support synchronized scaling, the Sync scale option is now enabled by default.

This makes it easier to create dashboards where text and content are visually balanced across comparable widgets, without having to enable synchronized scaling manually for each widget.

The setting can still be disabled where independent scaling is preferred.

IG-2644 New design grid for easier widget alignment​

Release notes​

Dashboard editing now includes a visual grid to make it easier to align widgets horizontally and vertically.

The grid is shown while dragging a widget when designing a dashboard and provides a visual reference for positioning widgets consistently across the canvas. It is only a guide, i.e. widgets are not snapped to the grid, so the existing fine-grained positioning remains unchanged.

The grid is designed to remain visible across the available dashboard themes.

IG-2646 New Stacked dashboard layout​

Release notes​

Dashboards now support a new Stacked widget layout that makes it easier to keep dashboards compact and organized while editing.

In Stacked mode, widgets automatically move upward to close empty gaps, and other widgets are moved aside when a widget is repositioned. This helps maintain a tighter and more structured dashboard layout without requiring manual adjustment of every gap.

When moving a widget in Stacked layout mode, the target area is highlighted while dragging, showing where the widget will be placed when released.

Stacked is the default layout for newly created dashboards.
Existing dashboards keep the Free layout to preserve their current widget positioning and avoid changing the intended dashboard design. The layout can be changed at any time from Dashboard settings.

The available modes are:

  • Free – widgets stay where they are placed and gaps are preserved.
  • Stacked – gaps are automatically closed and widgets are repositioned as needed when editing the dashboard.

IG-2647 Easier access to and exploration of the External API​

Release notes​

The External API is now easier to access, understand and test directly from DCC.

The API Keys tab under IoT Administration now brings the relevant API resources together in one place. From here, you can create and manage API keys, open the updated External API guide, or launch the new interactive OpenAPI reference for the current DCC environment.

The interactive API reference provides the available endpoints, parameters, authentication requirements, and request and response formats, and allows requests to be tested directly against the selected DCC environment. The accompanying guide has also been expanded with practical guidance on authentication, locating device and Data Refinement Field IDs, timestamps, aggregation and request examples.

This makes it significantly easier for developers to explore the DCC API and start building external integrations without having to piece together information from several different places.

The API guide on the documentation site https://documentation.inuatek.com/docs/external-api will be updated with this info when 7.4 is live.

IG-2648 Support for Advantech ADAM-6000 devices​

Release notes​

DCC now supports direct MQTT connectivity from Advantech ADAM-6000 series I/O modules.

When creating a device in DCC, Advantech ADAM-6000 Series can now be selected as the device type. DCC generates the required device-specific MQTT configuration and CA certificate, which can then be applied through the Advantech I/O Module Utility.

Once connected, selected ADAM input and output channels are automatically created as sample points in DCC and can be used in dashboards, Data Viewer, alerts, reports, and other platform functions.

The integration uses MQTT over TLS and supports configurable publishing intervals, deadband settings, timestamps, and user-defined signal names.

A new step-by-step guide for connecting and configuring ADAM-6000 devices will become available on the documentation site https://documentation.inuatek.com/docs/mqtt with the 7.4 release.

IG-2654 Include equation inputs and select timezone in CSV reports​

Release notes​

CSV reports generated from Next-Gen dashboards now provide more control over both the included data and timestamp format.

Sample points used as additional datasources in an equation can now also be included in the CSV report, even when they are not configured as direct datasources in the widget. In the report selection, these are shown as Equation inputs below the relevant datasource.

When generating a CSV report, you can now choose between:

  • UTC
  • Local Time – based on the timezone reported by the user's web browser
  • Device Time – based on the configured timezone of the selected device

The selected timezone is applied consistently to all timestamps in the exported CSV and is also indicated in the date/time column header, making the time context of the exported data clear.

For example, a user whose browser reports the Europe/Copenhagen timezone will see this reflected when Local Time is selected.

This makes CSV exports easier to use across different locations and devices while also allowing equation inputs to be included alongside the primary dashboard data.

IG-2655 Clarify the Data Refinement field display-mode slider in Line chart widgets​

Release notes​

The display-mode slider now uses the labels Show translations and Show raw values, with a tooltip explaining the difference between displaying the field’s configured translations as symbols and plotting its underlying numeric values.

Translation settings are preserved when switching between modes, so you can return to Show translations without reconfiguring your selections.

IG-2698 Consistent ordering of translated values in Event View​

Release notes​

Translated values in the Event View now follow the same display order as Value widgets: symbol, translated text, and raw data.

This makes translated events easier to read and prevents the content from visually shifting as the raw value changes.

The corresponding display options in the widget configuration have also been reordered to follow the same principle.

Bug Fixes​

IG-2645 Improved widget scaling behavior​

Release notes​

We have improved the automatic scaling behavior used by dashboard widgets.

The List widget now scales independently and is no longer synchronized with Table and Event widgets. This avoids inconsistent font sizing between widget types that use different content and layout structures.

In addition, automatic font sizing has been improved across supported widgets, giving text more available space and producing more consistent scaling within the widget.

This addresses scaling inconsistencies introduced with the earlier synchronized scaling features.

IG-2660 Status Bar now respects Exclude Default Translation​

Release notes​

Fixed an issue in the Status Bar widget where default Data Refinement translations were always excluded, regardless of the Exclude Default Translation setting.

The setting now works as intended, allowing default translations to be either shown or excluded from the Status Bar depending on the widget configuration.

This issue was specific to the Status Bar and does not affect other widgets.

IG-2670 Fixed repeated sample point configuration events​

Release notes​

Fixed an issue where some devices could repeatedly log Sample point configuration changed events even though their configuration had not actually changed.

The configuration check now correctly matches settings to the relevant sample point, so unchanged devices no longer generate repeated events.

For devices using a Streaming Only license, sample points also remain consistently configured as realtime only.